Crane risk logic apparatus and system and method for use of same

ABSTRACT

A crane risk logic apparatus and system and method for use of the same are disclosed. In one embodiment of the crane risk logic apparatus, the crane risk logic apparatus is integral with a crane, such as a mobile or crawler crane or a tower crane, and located in communication with a load moment indicator. The crane risk logic apparatus receives crane data from the load moment indicator and determines various data analytics, such as, lift angle data, allowable capacity data, operator override data, anti-two-block activation data, operational time data, lift cycle count data, lift classification data, slewing speed data, wind speed data, warning message data, error message data, and winch direction and speed data for each crane lift cycle. The data analytics may be utilized to inform a crane operator evaluation or a crane maintenance schedule for the crane, for example.

PRIORITY STATEMENT & CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority from U.S. Provisional PatentApplication No. 63/068,232, entitled “Crane Risk Logic Apparatus andSystem and Method for Use of Same” and filed on Aug. 20, 2020, in thename of Jim D. Wiethorn; which is hereby incorporated by reference, inentirety, for all purposes.

TECHNICAL FIELD OF THE INVENTION

This invention relates, in general, to cranes and, in particular, to acrane risk logic apparatus and system and method for use of the same formobile cranes, tower cranes, and the like, that enables crane owners,and operators to provide a means of evaluating crane use and operationalprocedures of the operator.

BACKGROUND OF THE INVENTION

An examination of accident data over the past thirty-five (35) years hasprovided critical data to aid crane forensics and the identification ofcauses of crane accidents—after the accidents have occurred. To betterpredict the likelihood of an accident before the accident occurs, abetter understanding of the complex interactions between an operator,crane, and load are required. To achieve such an understanding, moreoperational data is required. Accordingly, there is a need for improvedsystems and methods to achieve these ends.

SUMMARY OF THE INVENTION

It would be advantageous to mitigate the risks of crane accidents inmobile cranes, tower cranes, and the like. It would also be desirable toenable a computer-based and mechanical-based solution that is easily andreliably deployed to collect data for the purposes of both crane useevaluation and operator evaluation. To better address one or more ofthese concerns, a crane risk logic (CRL) apparatus for cranes, and thelike, and systems and methods for use of the same are disclosed. In oneembodiment of the CRL apparatus, the CRL apparatus is integral with, andlocated in, mobile and tower cranes having a load moment indicator. TheCRL apparatus receives crane data from mechanical devices and the loadmoment indicator and determines various data analytics, such as, liftangle data, allowable capacity data, operator override data,anti-two-block activation data, operational time data, lift cycle countdata, lift classification data, slewing speed data, wind speed data,warning message data, error message data, and winch direction and speeddata for each crane lift cycle. The data analytics may be utilized toperform a crane operator evaluation or develop a crane maintenanceschedule for the crane, for example. A system and method, whichaccompany the CRL apparatus, are also disclosed. This CRL apparatus,along with the system and method and other aspects of the invention willbe apparent from and elucidated with reference to the embodimentsdescribed hereinafter.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the features and advantages of thepresent invention, reference is now made to the detailed description ofthe invention along with the accompanying figures in which correspondingnumerals in the different figures refer to corresponding parts and inwhich:

FIG. 1 is a schematic illustration depicting one embodiment of a systemutilizing crane risk logic (CRL) apparatuses on multiple cranes,according to the teachings presented herein;

FIG. 2 is a functional block diagram depicting one embodiment of a loadmoment indicator shown FIG. 1, which may form a portion of the CRLapparatus;

FIG. 3 is a functional block diagram depicting one embodiment of a CRLapparatus shown FIG. 1, according to the teachings presented herein;

FIG. 4 is a functional block diagram depicting one embodiment of aserver shown in FIG. 1, which may form a portion of the system;

FIG. 5 is a conceptual module diagram depicting a software architectureof a CRL application of some embodiments; and

FIG. 6 is a flowchart depicting one embodiment of a method utilizing aCRL apparatus on a crane, according to the teachings presented herein.

DETAILED DESCRIPTION OF THE INVENTION

While the making and using of various embodiments of the presentinvention are discussed in detail below, it should be appreciated thatthe present invention provides many applicable inventive concepts, whichcan be embodied in a wide variety of specific contexts. The specificembodiments discussed herein are merely illustrative of several specificways to make and use the invention, and do not delimit the scope of thepresent invention.

Referring initially to FIG. 1, therein is depicted one embodiment of asystem for providing crane risk logic (CRL) that is schematicallyillustrated and generally labeled 10. A crawler crane 12 and a towercrane 14 are positioned in field F at a job site. It should beappreciated that although a crawler crane and a tower crane aredepicted, the teachings presented herein work with any type of crane. Asshown, the crawler crane 12 includes a crane body 16 having a boom 18mounted thereto so as to be raised and lowered. Additionally, a lowerundercarriage 20 with a set of parallel tracks 22 having endless treads24 provide stability and mobility to the crawler crane 12. Winchassembly 26, which includes, in one embodiment, a boom hoist winch 23, aload line winch 25, and an auxiliary line winch 27, is also secured tothe crane body 16 to drive the boom 18 to be raised and lowered througha gantry 28 and boom hoist assembly 30. In one implementation, a hoistcable 32 is drawn out of the boom hoist winch 23 along the boom 18 andis suspended from the extreme end of the boom 18 to suspend a hook 34suspended by wire ropes. By the hoist means constituted as describedabove or an alternative thereto, the main winding and hoisting work forraising and lowering mainly a very heavy load L₁, depicted as beams, bylifting and then placing the load, thereby completing a lift cycle,which is identified as a lift cycle LC₁. Safety features, such as asiren 36 mounted on the top of the crane body 16, provide variousnotifications and precautions to improve safety when a load momentindicator (LMI) 38 is overridden or overloaded. It should be appreciatedthat although one embodiment of a winch assembly 26 is depicted, otherconfigurations of winches are within the teachings presented herein andthe winch design selected will depend on various crane engineeringfactors and intended operational capability of the crane.

The LMI 38 is secured to the crawler crane 12 to monitor crane functionsto provide an operator of the crawler crane 12 with a continuous readingof a rated capacity of the crawler crane 12 as the crawler crane 12 andthe boom 18 move through motions to make a lift of the load L₁ tocomplete the lift cycle LC₁. The severity of a load cycle is based onthe relationship of the load weight to the allowable load permitted bythe load chart and expressed as a percent capacity. The system 10 maydetail the severity of each cycle based on the percent capacity of eachcycle. A CRL apparatus 50 having a housing 52 is located integral withthe crawler crane 12 and located in communication with the load momentindicator 38. As will be discussed in further detail hereinbelow, theCRL apparatus 50 collects crane data and crane analytics for monitoringand reporting purposes, and maintains the location of the crawler crane12, among other applications.

The tower crane 14 includes a foundation 64 with a tower 66 extendingtherefrom. A jib 68 extends horizontally to the tower 66 so as to rotatein a horizontal plane under the power of a slewing unit 70 positioned ontop of the tower 66. An operating cabin 72 sits above the slewing unit70 and rotates with the jib 68. A counter jib 74 holds counterweights, ahoist motor, a hoist drum, and electronics, for example, to drive thehoisting and the other functions. The jib 68 is supported by a fixedpendant 78 secured at a tower top 75 to an attachment point on the jib68. A wire rope hoist cable 77 is drawn out of a load line drum 79 witha motor located on the counter jib 74 and extends up/down the tower top75 and along the jib 68 and is suspended from a trolley (not shown) thattravels along the jib 68 to suspend a hook 80 suspended by multiplecables. By the hoist means constituted as described above, the mainwinding and hoisting work for raising and lowering mainly a very heavyload L₂, depicted as beams. From the point a load is lifted and lowereddefines a lift cycle LC₂. The severity of a load cycle is based on therelationship of the load weight to the allowable load permitted by theload chart or LMI and expressed as a percent capacity. The system 10 maydetail the severity of each lift cycle, such as the lift cycle LC₁ orthe lift cycle LC₂, based on the percent capacity of each cycle as wellas tracking other metrics.

An LMI 88 is secured to the tower crane 14 to monitor crane functions toprovide an operator of the tower crane 14 with a continuous reading of arated capacity of the tower crane 14 as the tower crane 14 and the jib68 move through motions to make a lift of the load L₂ to complete thelift cycle LC₂. A CRL apparatus 100 is located integral with the towercrane 14 and located in communication with the load moment indicator 88.As will be discussed in further detail hereinbelow, the CRL apparatus100 collects crane data and crane analytics for monitoring and reportingpurposes and maintains the location of the tower crane 14.

As shown, a CRL server 110 having a housing 112 and access to a CRLdatabase 114 provides an interface and functionality to the field F,including the CRL apparatus 50 associated with the crawler crane 12 andthe CRL apparatus 100 associated with the tower crane 14. An off-siteowner 116 is located in communication with the services offered by theCRL server in a cloud C. The off-site owner 116 may run various reports,such as an operator evaluation report 188 and a crane use report 120 togive visibility into how the crawler crane 12 or the tower crane 14 arebeing operated in the field F. This can also identify any potentialhazardous operations or abuse as well as inform an operator evaluationor maintenance schedule for the crawler crane 12 and the tower crane 14.

As previously mentioned, an examination of accident data over the yearshas provided critical data in the identification of crane accidents.Non-accident data can also reveal some interesting and potentiallycritical factors associated with future incidents based on thehistorical operational practices by the crane operator and themaintenance schedule of the crane. Although it is clear that an off-siteowner 116 cannot control every operational movement of the crane by theoperator, nor can the off-site owner 116 know or control the thoughtprocess of the crane operator, a study of the operational movements of acrane through the load moment indicator 38 of the crawler crane 12 orthe load moment indicator 88 of the tower crane 14, prior to accidents,can prevent accidents. That is, analysis of on-going non-accidentoperational data can be used to establish capabilities and traits ofoperators, as well as to document inherent risk factors and trendsestablished by collecting this data over a period of time. The CRLapparatus 50 and the CRL apparatus 100 as well as the system 10 storeongoing data of operators and cranes during normal operations andevaluates performance for use by the off-site owner 116 to evaluateperformance. In one implementation, the evaluation may also be used tosatisfy certification or accreditation requirements as represented by acertification agency 122, which is depicted as, but not limited to,OSHA. As shown, the certification agency 122 may receive a certificate124 relative to the evaluation of an operator or evaluation of a crane.The certificate 124 may be issued by a manager of the crane serviceserver 112, for example, or another entity.

With respect to monitoring and reporting purposes, in operation, each ofthe CRL apparatuses 50, 100 receives crane data and, in particular, LMIdata, from the respective load moment indicators 38, 88 and determineslift cycle data therefrom. In general, lift cycles are the number oftimes that a crane is loaded at a particular boom angle, lifts the load,and then releases the load at a second boom angle. Lift cycles becomevery critical once the load is 80% of the allowable load. Therefore, inone implementation, the CRL apparatus 50 interfaces with a load chartthat forms a portion of the LMI data provided by the load movementindicator 38 at the crawler crane 12. The CRL apparatus 50 documents alllift cycles with particular attention to lift cycles over certain limitsthat can be preset by the crane owner. By way of example, the CRLapparatus 50 may categorize and count each lift cycle into 4 distinctlevels of severity; namely, by way of example, Light (<70% capacity);Normal (70-90% capacity); Heavy (90-95% capacity; and Severe (>95%capacity). Precise documentation of the crane usage based on number andseverity of lift cycles provides critical information for maintenanceand inspection requirements. Additional information may be gathered formobile cranes conducting low boom angle lifts. The low-boom angle limitis set by the owner and notifies them when a certain number (limit) haveoccurred. Similarly, this knowledge allows to control severe and abuseto the crane.

Referring to FIG. 2, in one embodiment, the load moment indicator (LMI)38 is constituted by a calculation processing portion 130, an automaticstop valve 132, an LMI data output 134, and one or more indicators 136.The calculation processing portion 130 may include a memory section 138,a load factor calculation section 140, and an override portion 141.Respective indicators 136 are provided and include, by way of example, aboom angle indicator 144 for detecting a boom angle, a guyline tensiondetector 146, a main hoist line load indicator 148 as a main windinghoist load detecting means for detecting a load (main side hoist load)of the hoist cable 32, and an auxiliary hoist line load indicator 150 asan auxiliary winding hoist load detecting means for detecting a load(auxiliary side hoist load) of auxiliary cabling and ropes. Detectionvalues obtained by each of the indicators 136 are input to the loadfactor calculation section 140. It should be appreciated that although aparticular configuration of detectors is presented, other detectorconfigurations are within the teachings presented herein. By way ofexample and not by way of limitation, the speed of the winches andmotors may be monitored by indicators for slewing and raising/loweringload measurements.

In one embodiment, the load factor calculation portion 140 may include awhole load factor calculation portion 150, a main side load factorcalculation portion 152, and an auxiliary side load factor calculationportion 154. The load factors, such as hoist load/rated load, relativeto the whole, main side and auxiliary side are calculated by thesecalculation portions 150, 152, 154. When the load factor reaches apredetermined value, an overload is judged by the override portion 141,and a stop signal is then sent to the automatic stop valve 132, whichmay be a solenoid valve, for example, and the crane operationautomatically stops. It should be appreciated that although onearchitecture of the load moment indicator 38 is provided, otherarchitectures are within the teachings presented herein. It should beappreciated that the load moment indicator 88 may be similar instructure and function to the load moment indicator 38.

By way of example and not by way of limitation, the following table,Table I, provides exemplary data sets, including crane data and dataanalytics, that are measured by the load moment indicator 38 and/or theCRL apparatus 50.

TABLE I LMI Data & Crane Data & Data Analytics Winch 1 (Main) Load onthe hook Winch in operation Raise or lowering winch speed Winch 2(Auxiliary) Load on the whip line Winch in operation Raise or loweringwinch speed Boom angle Angle of the boom Luffing jib angle Angle of theluffing jib Interface with main line Load being lifted load chart %capacity of the allowable Overload condition Override warning Interfacewith whip line Load being lifted chart % capacity of the allowableOverload condition Override warning Wind speed Anemometer readingWarning over 20 mph Warning over 25 mph Stop work over 30 mph Anti-TwoBlock Activation Date-Time of Activation Override notification LiftCycle Load Take on load % capacity of lift boom angle 1-Let off load %capacity lift boom angle 2 Actual load/Allowable load <70% Number ofLight Cycles [Most defining cycles are 70-90% Number of Normal above 80%of the load] Cycles 90-95% Number of Heavy Cycles >95% Number of SevereCycles Hours of Operation Time a crane has been working and availableLift Cycle Number Number of lift cycles Lift Cycle Type Type of liftcycles Change in Boom Angle Change in the angle of the boom OverrideActivation Interrupt the action of an automatic safety-related functionSlewing Speed Angular movement of a crane boom or crane jib in ahorizontal plane Warning Message Alert to the operator of a conditionthat might cause a problem Error Message Alert to the operator of anunexpected, problematic condition Winch Speed Speed and direction of awinch

The LMI data output 134 may provide the CRL apparatus 50 with variousdata analytics 160. By way of example, and not by way of limitation, thedata analytics 160 identified by the CRL apparatus 50 via the LMI dataoutput 134 may include amount of load lifted 161, hours of operationdata 162, lift cycle data 164, percent of allowable data 166, boom angledata 168, change in boom angle data 170, A2B activation data 172,override activation data 174, slewing speed data 176, wind speed data178, warning message data 180, error message data 182, and winchdirection and speed data 184. The amount of load lifted 161 may recordthe weight of loads in each of the lift cycles that is actually lifted.The hours of operation data 162 may define for each crane cycle the timethe crane has been working and available. The lift cycle data 164 mayinclude the number of lift cycles with for each of the crane lift cycle,the type/severity of lift cycles. The percent of allowable data 166 mayinclude the percent of allowable load. The boom angle data 168 mayinclude information about the angle of the boom. The change in boomangle data 170 may include the change in the boom angle. The A2Bactivation data 172 may include information about activation of ananti-two-block system, which is standard among all cranes. The overrideactivation data 174 may include information about any overrides thatoccurred. The slewing speed data 176 may include information about theangular movement of a crane boom or crane jib in a horizontal plane asit relates to the suspended load. The wind speed data 178 may includeinformation about the wind speed, maximum wind speed and directionduring a lift cycle. The warning message data 180 may includeinformation about various warning messages and, analogously, the errormessage data may include information about error messages. The winchdirection and speed data 184 may include information about the speed anddirection of the winch movement. Additionally, each of the various dataanalytics 160 may also include Global Positioning System (GPS) data suchas date-stamped location.

Referring now to FIG. 3, within the housing 52, in one embodiment of theCRL apparatus 50, a processor 200, memory 202, storage 204, and one ormore transceivers 206 are interconnected by a bus architecture 208within a mounting architecture that supports an LMI data input 210,which is coupled to the LMI data output 134, inputs 212, outputs 214, adisplay 216, and a Global Positioning System (GPS) unit 218. It shouldbe understood that the processor 200, the memory 202, the storage 204,the inputs 212, the outputs 214, the display 216, and the GPS 218 may beentirely contained within the housing 52. The processor 200 may processinstructions for execution within the computing device, includinginstructions stored in the memory 202 or in the storage 204. The memory202 stores information within the computing device. In oneimplementation, the memory 202 is a volatile memory unit or units. Inanother implementation, the memory 202 is a non-volatile memory unit orunits. The storage 204 provides capacity that is capable of providingmass storage for the CRL apparatus 50. It should be appreciated that theCRL server 110 and CRL database 114 may provide additional storagecapacity in the cloud C for the CRL apparatus 50. Various inputs 212 andoutputs 214 provide connections to and from the computing device,wherein the inputs 212 are the signals or data received by the CRLapparatus 50, and the outputs 214 are the signals or data sent from theCRL apparatus 50.

The one or more transceivers, which are depicted as a transceiver 206,are associated with the CRL apparatus 50 and communicatively disposedwith the bus 208. As shown, the transceiver 206 may be internal,external, or a combination thereof to the housing. Further, thetransceiver 206 may be a transmitter/receiver, receiver, or an antennafor example. Communication between various devices and the CRL apparatus50 may be enabled by a variety of wireless methodologies employed by thetransceiver 206, including 802.11, 3G, 4G, Edge, WiFi, ZigBee, nearfield communications (NFC), Bluetooth low energy and Bluetooth, forexample. The display 216, which is optional, provides an electronicdevice for the visual display of information. The GPS unit 218 accessesa global navigation satellite system that uses a receiver and algorithmsto provide location, velocity and time synchronization to providelocationing information for the GPS unit 218, and, in turn, the CRLapparatus 50 and the crawler crane 12. It should be appreciated thatalthough one architecture of the CRL apparatus 50 is provided, otherarchitectures are within the teachings presented herein. Further, itshould be appreciated that the CRL apparatus 100 is similar in structureand function to the CRL apparatus 50.

The memory 202 and the storage 204 are accessible to the processor 200and include processor-executable instructions that, when executed, causethe processor 200 to execute a series of operations. In one embodimentof processor-executable instructions, the processor 200 is caused toreceive the LMI data at the load moment indicator data input 210. Theprocessor-executable instructions may then cause the processor toidentify, based on the received crane data, for each of the crane liftcycle or an aggregate thereof, one or more of the following: the liftangle data, the allowable capacity data, the operator override data, theanti-two-block activation data, the operational time data, the liftcycle count data, the lift classification data, the slewing speed data,the wind speed data, the warning message data, the error message data,and the winch direction and speed data for each of the crane lift cycleor a number of crane lift cycles.

The processor 200 is then caused to store data analytics at the storage204. The data analytics may be the lift angle data, the allowablecapacity data, the operator override data, the anti-two-block activationdata, the operational time data, the lift cycle count data, the liftclassification data, the slewing speed data, the wind speed data, thewarning message data, the error message data, or the winch direction andspeed data. The processor-executable instructions may then cause theprocessor 200 to send the data analytics to a server, such as the CRLserver 110 that may be cloud-based.

The processor-executable instructions presented hereinabove with FIG. 3include, for example, instructions and data which cause a generalpurpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Processor-executable instructions also include program modules that areexecuted by computers in stand-alone or network environments. Generally,program modules include routines, programs, components, data structures,objects, and the functions inherent in the design of special-purposeprocessors, or the like, that perform particular tasks or implementparticular abstract data types. Processor-executable instructions,associated data structures, and program modules represent examples ofthe program code means for executing steps of the systems and methodsdisclosed herein. The particular sequence of such executableinstructions or associated data structures represents examples ofcorresponding acts for implementing the functions described in suchsteps and variations in the combinations of processor-executableinstructions and sequencing are within the teachings presented herein.

Referring now to FIG. 4, one embodiment of the CRL server 110 as acomputing device includes, within the housing 112, a processor 220,memory 222, and storage 224 interconnected with various buses 226 in acommon or distributed, for example, mounting architecture that alsosupports inputs 228, outputs 230, and network interface 232. In otherimplementations, in the computing device, multiple processors and/ormultiple buses may be used, as appropriate, along with multiple memoriesand types of memory. Further still, in other implementations, multiplecomputing devices may be provided and operations distributedtherebetween. The processor 220 may process instructions for executionwithin the server 120, including instructions stored in the memory 222or in storage 224. The memory 222 stores information within thecomputing device. In one implementation, the memory 222 is a volatilememory unit or units. In another implementation, the memory 222 is anon-volatile memory unit or units. Storage 224 includes capacity that iscapable of providing mass storage for the CRL server 110, including CRLdatabase storage capacity. Various inputs 228 and outputs 230 provideconnections to and from the server 120, wherein the inputs 228 are thesignals or data received by the CRL server 110, and the outputs 230 arethe signals or data sent from the CRL server 110. The network interface232 provides the necessary device controller to connect the CRL server110 to one or more networks.

The memory 222 is accessible to the processor 220 and includesprocessor-executable instructions that, when executed, cause theprocessor 220 to execute a series of operations. Theprocessor-executable instructions cause the processor 220 to provide aninterface for an off-site crane owner. The processor-executableinstructions also cause the processor 220 to maintain the CRL database114 in the storage 224. As discussed, the CRL database 114 may includeinformation about the crane owner, a crane operator of the crane, craneinformation, and job information. The processor 220 is caused to receivethe crane data and the lift cycle data from the CRL apparatus 50 andappend the crane data to the CRL database 124. The processor-executableinstructions may cause the processor 220 to receive the data analyticsfrom the CRL apparatus 50. In one embodiment, following the receipt ofthe data analytics, the CRL server 110 is caused via the processor 220to evaluate the performance of the operator using the data analytics. Inanother embodiment, following the receipt of the data analytics, the CRLserver 110 is caused via the processor 220 to evaluate the crane usingthe data analytics. The processor-executable instructions may cause theCRL server 110 to generate a report, such as the operator report 118 orthe crane report 120.

The CRL server 110 and the CRL apparatus 50 provide an analysis ofon-going non-accident operational data that can be used to establishcapabilities and traits of operators, as well as to document inherentrisk factors and trends established by collecting this data over aperiod of time. The CRL apparatus 50 stores ongoing data of operatorsduring normal operations and with the use of the CRL server 110evaluates performance for use by owners to evaluate their performance inaccordance with various requirements, such as OSHA requirements. By wayof example, with the CRL apparatus 50 and the CRL server 110, cranelifts are identified that are made below a specified angle whichsignificantly increases the load in boom hoist wire ropes and itscorresponding life. The owner is notified of improper operations and isable to intercede before the wire rope is damaged to failure. Currently,owners have no means of accurately determining the life of wire rope orguidance for proper inspection. By establishing the degree level of liftcycles (low, normal, heavy, or severe), a more definitive maintenanceschedule can be established based on the type of use.

By way of further example, the CRL apparatus 50 and the CRL server 110document the severity level of lifts that the operator conducts. The CRLapparatus 50 and the CRL server 110 collect the data of the normalpercentage of allowable capacity of each lift and plots thenormal-to-actual range of the lifts. Consistently high levels of percentallowable capacity can be addressed by crane placement or boomconfiguration. The CRL apparatus 50 and the CRL server 110 document thecount of operator override of the load limiter, as well as theoccurrence of anti-2-block (A2B) activation. A consistent overload andcorresponding overriding the load limiting device requires attention bythe owner to address with the operator.

The processor-executable instructions presented hereinabove with FIG. 4include, for example, instructions and data which cause a generalpurpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Processor-executable instructions also include program modules that areexecuted by computers in stand-alone or network environments. Generally,program modules include routines, programs, components, data structures,objects, and the functions inherent in the design of special-purposeprocessors, or the like, that perform particular tasks or implementparticular abstract data types. Processor-executable instructions,associated data structures, and program modules represent examples ofthe program code means for executing steps of the systems and methodsdisclosed herein. The particular sequence of such executableinstructions or associated data structures represents examples ofcorresponding acts for implementing the functions described in suchsteps and variations in the combinations of processor-executableinstructions and sequencing are within the teachings presented herein.

FIG. 5 conceptually illustrates the software architecture of a CRLapplication 250 of some embodiments that may render information, such asthe operator report 118 and the crane report 120. In some embodiments,the CRL application 250 is a stand-alone application or is integratedinto another application, while in other embodiments the applicationmight be implemented within an operating system 280. Furthermore, insome embodiments, the CRL application 250 is provided as part of aserver-based solution or a cloud-based solution. In some suchembodiments, the application is provided via a thin client. That is, theapplication runs on a server while a user interacts with the applicationvia a separate machine remote from the server. In other suchembodiments, the application is provided via a thick client. That is,the application is distributed from the server to the client machine andruns on the client machine.

The CRL application 250 includes a user interface (UI) interaction andgeneration module 252, management (user) interface tools 254, aggregatormodules 256, filter modules 258, crane report modules 260, operatorreport modules 262, notification/alert modules 264, a database module266, and an owner module 268. The CRL application 250 has access to theCRL database 114, which in one embodiment, may include crane data 270,crane evaluation metrics 272, operator data 274, operator evaluationmetrics 276, and presentation instructions 278, which presentsinstructions for the operation of the CRL application 250. In someembodiments, storages 270, 272, 274, 276, 278 are all stored in onephysical storage. In other embodiments, the storages 270, 272, 274, 276,278 are in separate physical storages, or one of the storages is in onephysical storage while the other is in a different physical storage.

The CRL database 114, in one implementation, provides a database of allpertinent information required for crane lifts and historicalinformation of the crane, owner, and operator. The crane data 270 may beall information concerning the make, model, and manufacturer of thecrane as well as the date of manufacture. A copy of a current annualinspection/certification of the crane, a copy of all maintenancerecords, and documentation of the purchase of the crane, includingcurrent ownership information, may be included in the crane data 270.The crane evaluation metrics 272 include various standards for measuringthe crane operation in a safe manner and maintaining the crane in a safecondition. The operator data 274 includes all the information of theoperator assigned to the crane such as all experience and particularlycertification documentation with a date of expiration. Recent “operatorevaluation forms” may be included. The CRL server 120 may track the lifeand expiration of such forms and certificates to provide notificationsprior to expiration when renewal is required. The operator evaluationmetrics 276 include various standards for ensuring the crane is operatedin a safe and workmanlike manner. The UI interaction and generationmodule 252 generates a user interface that allows the end user tospecify parameters that may be utilized to generate various reports andnotifications.

Once the parameters have been established for the generation of reportsby default or by an end user utilizing the management (user) interfacetools 254, the aggregator modules 256 and the filter modules 258 may beexecuted to analyze instances or summaries of LMI data and crane datagathered by the CRL application 250 by applying selected performancecharacteristic or selected performance characteristics to the instancesof the LMI data and the crane data. The crane report modules 260 andoperator report modules 162 may be executed to containerize and annotatethe data elements to generate the required report or reports. The cranereport modules 260 and operator report modules 162 may also assist aninvestigator or owner in the event of incident occurring as well asproviding information on operator evaluation and crane maintenance. Thecloud C and, in particular, the CRL database 114 captures and stores alldata, which can be used to generate various reports to inform anevaluation. Additionally, by way of example, the crane report reportsmodules 260 may generate crane usage reports that allow an owner todetermine actual hours of use for financial evaluation of each crane. Byway of further example, the crane report modules 260 may also providedetailed records about the service times and hours of each crane. Suchrecords may be an asset for insurances purposes and stored at a mainoffice of the owner.

The notification/alert modules 262 may be executed to providenotifications of varying levels of urgency to the off-site owner 116 orthe operator O at the field F, for example. The notifications and alertsmay be weather related or job-site related or crane-related, forexample. The database module 266 may be executed to obtain data from theCRL database 124. The owner module 268 provides the necessary interfaceor interfaces for the owner of the crane.

In the illustrated embodiment, FIG. 5 also includes an operating system280 that includes input device driver(s) 282 and a display module 284.In some embodiments, as illustrated, the input device drivers 282 anddisplay module 284 are part of the operating system 280 even when theanalytics application 250 is an application separate from the operatingsystem 280. The input device drivers 282 may include drivers fortranslating signals from a keyboard, mouse, touchpad, tablet, touchscreen, gyroscope or accelerometer, for example. A user may use one ormore of these input devices 282, which send signals to theircorresponding device driver, in combination with the display module 284to interact with the CRL application 250. The device driver thentranslates the signals into user input data that is provided to the UIinteraction and generation module 252.

Referring to FIG. 6, one embodiment of a method for utilizing a CRLapparatus on a crane is shown. The methodology starts at block 300 withthe CRL apparatus located on a crane and in communication with acloud-based CRL server having access to a CRL database. At decisionblock 302, if the crane is in a designated operational mode and preparedfor lifting then the methodology advances to block 304, where operatorinformation is collected and sent to the CRL server. At block 306, anoperational notification with the operator information is sent to theCRL server. At block 308, the CRL apparatus receives LMI data, which theCRL apparatus sends to the CRL server with data analytics at block 310.At decision block 312, if the crane is still in the designatedoperational mode or modes then the methodology returns to block 308;otherwise, the methodology advances to block 314. The CRL server makessubstantially real-time and current crane data available for analysis sothat both operator performance and crane function may be established andevaluated. This occurs at block 314 prior to a crane report beinggenerated at block 316 and an operator report being generated at block318. The methodology ends at block 320.

The order of execution or performance of the methods and techniquesillustrated and described herein is not essential, unless otherwisespecified. That is, elements of the methods and techniques may beperformed in any order, unless otherwise specified, and that the methodsmay include more or less elements than those disclosed herein. Forexample, it is contemplated that executing or performing a particularelement before, contemporaneously with, or after another element are allpossible sequences of execution.

While this invention has been described with reference to illustrativeembodiments, this description is not intended to be construed in alimiting sense. Various modifications and combinations of theillustrative embodiments as well as other embodiments of the invention,will be apparent to persons skilled in the art upon reference to thedescription. It is, therefore, intended that the appended claimsencompass any such modifications or embodiments.

What is claimed is:
 1. A crane risk logic apparatus for a crane, thecrane risk logic apparatus comprising: a housing securing a load momentindicator input, a processor, memory, a global positioning system unit,and a wireless transceiver thereat, the load moment indicator inputbeing configured to interface with a load moment indicator secured tothe crane and receive crane data therefrom; a busing architecturecommunicatively interconnecting the load moment indicator input, theprocessor, the memory, the global positioning system unit, and thewireless transceiver; and the memory accessible to the processor, thememory including processor-executable instructions that, when executed,cause the processor to: receive the crane data at the load momentindicator input, identify, based on the received crane data, lift angledata for each crane lift cycle, identify, based on the received cranedata, a load amount and allowable capacity data for each of the cranelift cycles, identify, based on the received crane data, operatoroverride data for each of the crane lift cycles, identify, based on thereceived crane data, anti-two-block activation data for each of thecrane lift cycles, store data analytics, the data analytics including atleast one of the lift angle data, the allowable capacity data, theoperator override data, and the anti-two-block activation data, and sendthe data analytics to a server, the server being a cloud-based serverservicing a plurality of crane risk logic apparatuses.
 2. The crane risklogic apparatus as recited in claim 1, wherein the data analytics informa crane operator evaluation.
 3. The crane risk logic apparatus asrecited in claim 1, wherein the data analytics inform a cranemaintenance schedule for the crane.
 4. The crane risk logic apparatus asrecited in claim 1, wherein the housing is integral with the crane. 5.The crane risk logic apparatus as recited in claim 1, wherein thehousing is integral with the crane, the crane being one of a mobilecrane and crawler crane.
 6. The crane risk logic apparatus as recited inclaim 1, wherein the housing is integral with the crane, the crane beinga tower crane.
 7. The crane risk logic apparatus as recited in claim 1,wherein the crane data further comprises data selected from the groupconsisting of crane geometrical data, main boom length, main boom angle,jib angle, jib length, operating mode, weight of load on a hook of thecrane, and total weight being lifted by the crane.
 8. The crane risklogic apparatus as recited in claim 1, wherein the memory accessible tothe processor further comprises processor-executable instructions that,when executed, cause the processor to identify, based on the receivedcrane data, operational time data for each of the crane lift cycles. 9.The crane risk logic apparatus as recited in claim 1, wherein the memoryaccessible to the processor further comprises processor-executableinstructions that, when executed, cause the processor to identify, basedon the received crane data, lift cycle count data.
 10. The crane risklogic apparatus as recited in claim 1, wherein the memory accessible tothe processor further comprises processor-executable instructions that,when executed, cause the processor to identify, based on the receivedcrane data, lift classification data for each of the crane lift cycles.11. The crane risk logic apparatus as recited in claim 1, wherein thememory accessible to the processor further comprisesprocessor-executable instructions that, when executed, cause theprocessor to identify, based on the received crane data, slewing speeddata for each of the crane lift cycle.
 12. The crane risk logicapparatus as recited in claim 1, wherein the memory accessible to theprocessor further comprises processor-executable instructions that, whenexecuted, cause the processor to identify, based on the received cranedata, wind speed data for each of the crane lift cycle.
 13. The cranerisk logic apparatus as recited in claim 1, wherein the memoryaccessible to the processor further comprises processor-executableinstructions that, when executed, cause the processor to identify, basedon the received crane data, warning message data for each of the cranelift cycle.
 14. The crane risk logic apparatus as recited in claim 1,wherein the memory accessible to the processor further comprisesprocessor-executable instructions that, when executed, cause theprocessor to identify, based on the received crane data, error messagedata for each of the crane lift cycle.
 15. The crane risk logicapparatus as recited in claim 1, wherein the memory accessible to theprocessor further comprises processor-executable instructions that, whenexecuted, cause the processor to identify, based on the received cranedata, winch direction and speed data for each of the crane lift cycle.